WARNING...This has had limited testing and should only be used with proper caution and understanding.  Call us if you are unsure.

If you do not want to install a Serial Command device, or understand this information fully, DO NOT install this test version.

GHE Server 2.7.a10

Prerelease of 2.7.10 implements new feature for sending Serial Data command strings to other devices on a COM port.  Devices like k4 on a USB connection, or KPA1500 or similar.  Uses the Virtual Switch device to trigger the send string.

There is no installer, the jar file included in this zip must be renamed to: "GH Everyware Server.jar" and placed in the program directory to replace the file of the same name.  The 2.7.a10 will show in the help|about screen when it's running this pre-release.  the directory is:

C:\Program Files (x86)\Green Heron Engineering\GH Everyware Server\

Once you are running Server 2.7.a10, verify everything appears working before adding a Serial Command Device.

1. Connect device via USB, or a USB> Serial Adapter, or a native serial port with the appropriate cable.  A COM port must be shown in Windows Device manager in order to set this up.

2. Use GH Server Device Manager to Name, select the COM port and the new type of "Serial Command".
	Click CONNECT and first time will be prompted for Baud Rate.  Once a device is CONNECTED, the entered Baud rate will be remembered, and the prompt will be skipped on subsequent re-starts.  If you need to change the baud, simply DISCONNECT the device, and then the next CONNECT will prompt again while showing the current value.  (This is the exact same behavior we use for FIXED or CLONED Rotators that need headings or offsets) 

	The Named Serial Command device will show as a rotator in the rotor tray, but with a heading of "---"  (we will create a special color/symbol for these with the real release when we can also make the appropriate change to the GHE Client.  You may hide this device once everything is working so that it doesn't take up space by using the Rotor Tray Display band map.  The Serial Commands will work regardless of the on-screen display of the Serial Command device.

3.  Create an appropriate button, band, or Map device using a Virtual Switch.  Then for each position in the switch, you can specify a different command to be sent with the Device Manager setups for Virtual Switch.  in the (...) menu for a position, enter the "Name" of the Serial Command device from #2, and in the 2nd column, enter the exact command string preceded with the '$' symbol.  You can also use other lines in each position to send commands to other devices, or to select other GHE Switch Devices (or rotator headings) using other features of the Virtual Switch.  Please see the release notes for the Virtual Switch full implementation 

This example is what the Virtual Switch (...) profile would look like to simply send the command "ME0075:0000;" to a connected K4 via a Serial Port (USB or USB->Serial adapter).

< sample screen >

Changes for 2.7.b10

1.	Added ability to send <cr> and <lf> control characters using "\r" and "\n" into Serial Command string.
2.	Add Serial Command via TCP and UDP network protocols.  These do NOT require a "connected" serial command device in device manager.  Instead, the ip addresses are added to the Virtual Switch in the Device Name field.
	Device Name
	TCP:192.168.4.91:9002			$Message send via TCP
	UDP:192.168.4.91:9052			$Message send via UDP
3.	Appropriate log messages are added.  Note that if the TCP device will not connect, it will throw an error and cause a momentary delay in the responses as the TCP connection time out.  GHE messages sends do not hold the TCP port open, so other devices, or other server commands can still access.
4.	We tested by including all three Serial Command methods in one Virtual Switch translation.  It sends a message via Serial COM port, TCP and UDP from one virtual switch position!

